Method and apparatus for maintaining a unified view of multiple mailboxes

ABSTRACT

A method of presenting a unified view of two mailboxes, each mailbox associated with a client is described. The unified view allows the user to see all actions she/he performed on a message in one mailbox performed in all other unified mailboxes. One of the clients has both a high cost, e.g. wireless, communication channel and a low cost, e.g. synchronization, communication channel. When a message is received by a client from its respective mailbox without an identifier, an identifier is generated and a copy of the message is sent to the other mailboxes with the identifier. When the user performs actions on a message with a client, the identifier for the message and the action can be conveyed to the other clients in a message to the other mailboxes. The unified view can be selectably updated either over the high cost communication channel or the low cost communication channel. The presence of two communication channels enables the cost of performing the unification to be contained. The user can select options to control the unification process and the use of the high cost communication channel, e.g. summarize messages over 250 words and/or remove attachments.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to the field of electronic messaging systems. Inparticular, the invention relates to a method and apparatus forpresenting a unified view of multiple mailboxes on multiple clients.

2. Description of the Related Art

Electronic message systems, or e-mail systems, enable widespreadcommunications. A typical person may have several mailboxes she/heaccesses with different clients, e.g. office computer and handheldcomputer. For example, Jane Doe might have a corporate mailbox“jdoe@corporate.com” as well as a mailbox with a wireless provider suchas “jdoe@wireless.com”. If Jane wishes to be able to receive and work onher messages both while at the office and while on the road she may wanta way to create a unified view of the two separate mailboxes on heroffice client and her handheld client.

Maintaining a unified view of messages sent to a single mailbox can betricky if the user accesses a single mailbox from multiple locations.Two separate Internet protocols provide varying degrees of support foraddressing this problem: the Post Office Protocol version 3 (POP3),defined by RFC 1939, and the Internet Message Access Protocol version 4(IMAP4), defined by RFC 1730.

With varying degrees of functionality, these protocols rely on mailagents such as Netscape™ Communicator™, Eudora™ or Microsoft™ OutlookExpress™ to maintain a partially unified view of a single mailboxaccessed from multiple locations. For example, using IMAP4, Jane Doe cansee her “jdoe@corporate.com” mailbox from her work using NetscapeCommunicator™ and she can see that same mailbox from home usingMicrosoft Outlook Express™. However, neither POP3 nor IMAP4 attempt toprovide a unified view of a message received at multiple mailboxes andstored on multiple clients.

Similarly, some handheld computers such as the Palm Connected Organizer™from 3Com Corporation, Santa Clara, Calif., enable a single mailbox tobe viewed on multiple clients through a HotSync™ process. Like POP3 andIMAP4, this process only addresses the viewing of a single mailbox frommultiple clients.

One approach some users take to handling multiple mailboxes is toforward all messages received at one mailbox to the other mailboxes. Forexample, if John Smith sent Jane Doe a message to her corporate mailbox,“jdoe@corporate.com”, Jane can set up her corporate mailbox so that allmessages are forwarded to her other mailboxes, including her wirelessmailbox, “jdoe@wireless.com”.

However, if Jane responds to the message from her handheld client whileviewing the wireless mailbox, there is no mechanism for reflecting thataction in her other mailboxes, including her corporate mailbox. Thus,when she next checks her other mailboxes, including her corporatemailbox, she will have to manually perform the actions she performed onthe message in the wireless mailbox.

For example, if she replied to the message on her handheld client andfiled it in a folder “Personal”, she would have to manually mark themessage as replied to and manually file the message in “Personal” whenshe next accesses her corporate mailbox. This manual system becomesincreasingly unwieldy as a person receives mote messages per day.

Also, wireless connectivity is costly. The price per transmission unitis typically high. Also, other cost factors such as battery drain fromtransmission and receiving exist. Therefore, it may not be desirable tofully reflect a standard mailbox to a wireless mailbox using the aboveforwarding technique. Also, this forwarding technique can create loopsthat cause messages to be sent in infinite loops. Therefore, it istypically necessary to forward messages to a particular mailbox only,e.g. corporate to handheld, but not handheld to corporate.

Accordingly, what is needed is a system supporting a unified view ofmessages from multiple mailboxes that allows actions performed on oneclient to be reflected in the unified view on other clients. Also, thesystem should work with handheld wireless computers without incurringhigh costs.

SUMMARY OF THE INVENTION

A method of presenting a unified view of two mailboxes, each mailboxassociated with a client is described. The unified view allows the userto see all actions she/he performed on one client reflected in all otherunified clients. For example, if a user receives a message from“tbrown@example.com” at her “jdoe@corporate.com” mailbox, that messagewill also appear in her other mailboxes being unified, e.g. her“jdoe@wireless.com” mailbox.

One of the clients, e.g. the handheld client, has both a high cost, e.g.wireless, communication channel and a low cost, e.g. synchronization,communication channel. The high cost communication channel may have aprice associated with transmitting information and their may benon-price cost factors such as battery consumption, bandwidth, and/orother factors that make the use of the high cost communication channelexpensive. In contrast the low cost communication channel is typicallyfree, e.g. docking cradle to desktop computer, and uses less power, etc.Thus, the two communication channels are used in conjunction to offer aunified view.

When a message is received by a client from its respective mailboxwithout an identifier, an identifier is generated and a copy of themessage is sent to the other mailboxes with the identifier. For example,when the client receives the message addressed to the“jdoe@corporate.com” mailbox from “tbrown@example.com”, there is noidentifier associated with the message. An identifier is generated and acopy of the message is sent to the other mailboxes that includes theidentifier. This allows actions performed on the message at a laterpoint on any of the clients to be reflected in the other clients.Messages received with an identifier can be displayed withoutmodification as these messages have already been handled by one of theother clients.

When the user performs actions on a message with a client, theidentifier for the message and the action can be conveyed to the otherclients in a message to the other mailboxes. For example, when Janedeletes the message with the identifier “jdoe@wireless.com:93” from herwireless client, a message can be sent to the other clients thatindicates the identifier and the action, here “deleted”.

The unified view can be selectably updated either over the high costcommunication channel or the low cost communication channel. Also,multiple actions can be batched into a single message to the othermailboxes.

The user can select options to control the unification process and theuse of the high cost communication channel, e.g. summarize messages over250 words and/or remove attachments. Other embodiments allow the use ofthe high cost communication channel to be further controlled by usingrules to control what flows over that channel and what is held for whenthe low cost communication channel is available. For example, messageswith a priority of urgent might be sent over the high cost communicationchannel, but other messages might be held until the lost costcommunication channel is available. Thus the use of two communicationchannels enables the cost of performing the unification to be containedeven when there are a large number of messages and or mailboxes to beunified.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a system including one embodiment of the invention.

FIGS. 2-5 are process flow diagrams describing the unification processaccording to various embodiments of the invention.

DETAILED DESCRIPTION A. Definitions

1. Message

A message, also an electronic mail message or an e-mail, is a communiquéfrom a person and/or machine to another person and/or machine. A messageis typically comprised of two parts: a header and a body. The headerincludes addressing and routing information. The body includes thecontents of the message, e.g. a memo, a short note, an attachment,and/or other contents. Users can send messages to other users and/ormachines by specifying an address for the recipient. Users can receivemessages from other users and/or machines at their mailboxes.

2. Mailbox

A mailbox is a storage area belonging to a user for messages. Eachmailbox is associated with one or more electronic mail addresses thatcan be used to send the user messages. On the Internet, electronic mailaddresses are comprised of a user identifier and a host name separatedby an “@” symbol, e.g. “jdoe@corporate.com”. Each mailbox has one, ormore, addresses associated with it.

Messages sent to the user's address are stored in the user's mailbox. Insome systems, the messages are stored on one or more servers. In othersystems, the messages are stored directly on the user's computer. Stillother systems mix the two approaches. For example, a UNIX server canprovide mailboxes to several thousand users with the POP3 protocoland/or the IMAP4 protocol. In this configuration, the user's mailbox isstored on the UNIX server until the user retrieves the messages toher/his computer.

A mailbox accessed using POP3 and/or IMAP4 and the user's copy of thatmailbox are considered a single mailbox. For example, if Jane Doeaccesses her “jdoe@corporate.com” mailbox using IMAP4, the portion ofthe mailbox on the UNIX server and the portion of the mailbox on hercomputer are considered a single mailbox.

Some mail agents such as Microsoft™ Outlook Express™, Netscape™Communicator™ and Qualcomm™ Eudora™ allow multiple mailboxes to beviewed on a single client. In this case, all of the mailboxes accessedby the user's mail agent can be treated as a single mailbox to beunified with the other mailboxes. For example, if Jane's corporatecomputer uses Eudora™ to access two mailboxes: “jdoe@corporate.com” and“webmaster@corporate.com”, then she can select to have either and/orboth mailboxes unified with her other mailboxes.

3. Action

The term action refers to activities relating to messages. For example,after reading a message with a client, a change is made to the messageon many systems to mark the message as read. Other examples of actionsinclude replying to a message, forwarding a message, classifying amessage, deleting a message, receiving a message, and/or other actions.

4. Unified View

The term unified view as it applies to messages, and mailboxes, meansthat the same message has the same status, filing location, etc., on allclients. For example, upon reading a message on one client, if themessage is marked read in the other mail agents, then the view isunified.

The unification process can take some time. For example, if a user ofthe Palm VII™ does not activate their wireless link often or synchronizetheir handheld with their desktop often, the view inside the Palm VII™client may not reflect the most current actions and messages received bythe other clients, and vice versa.

B. System Overview

FIG. 1 illustrates a system including one embodiment of the invention.In the system of FIG. 1, a unified view is being provided of twomailboxes: a corporate mailbox and a wireless mailbox. The corporatemailbox could be a Microsoft Exchange™ mailbox hosted on Windows NT™, orsome other type of mailbox. The wireless mailbox could be a Palm.Net™wireless mailbox for a Palm VII™ Connected Organizer from 3ComCorporation, Santa Clara, Calif., or some other type of wirelessmailbox. Although only two mailboxes are shown, some embodiments of theinvention support more than two mailboxes.

The following paragraph lists the elements of FIG. 1 and describes theirinterconnections. FIG. 1 includes a mailbox 100, a mailbox 102, ahandheld client 108, and a client 110. The handheld client 108 includesa unifier 112. The client 110 includes a unifier 114. An address 104 isassociated with the mailbox 100. An address 106 is associated with themailbox 102. The client 110 has a communication channel 116 with themailbox 102 and a communication channel 118 with the mailbox 100. Thehandheld client 108 has a high cost communication channel 120 with themailbox 100 and a low cost communication channel 122 with the client110. The following describes the use of the elements of FIG. 1. Themailbox 100 and the mailbox 102 are mailboxes such as a UNIX mailbox, asimple mail transfer protocol (SMTP) mailbox, a Microsoft Exchange™mailbox, a Lotus Notes™ mailbox, a wireless mailbox, a POP3 mailbox, anIMAP4 mailbox, and/or some other type of mailbox. In this example, themailbox 100 is a Palm.Net™ wireless mailbox. In this example, themailbox 102 is a POP3 mailbox.

The address 104 and the address 106 allow messages to be sent to therespective mailboxes 100 and 102. In this example, the address 104 is“jdoe@wireless.com” and the address 106 is “jdoe@corporate.com”.

The handheld client 108 and the client 110 are devices with softwareand/or hardware for accessing the respective mailboxes 100 and 102. Thehandheld client 108 and the client 110 could be computers, thin clientcomputers, set-top boxes, hand held computers, cellular telephones,pagers, and/or some other type of device. In this example, the handheldclient 108 is a Palm VII™ and the client 110 is a computer.

The communication channel 116 and the communication channel 118 can beof several types such as a network channel, a dial-up channel, awireless channel, and/or some other type of channel. Additionally,multiple types can be used in combination. For example, a dial-upchannel and a network channel could be used on a laptop depending onwhether the laptop is coupled to a network or dialing in to a network.In this example, the client 110 is connected to a local area network(LAN) such as an Ethernet network for communication with the mailbox102.

The handheld client 108 has two channels: the high cost communicationchannel 120 and the low cost communication channel 122. The high costcommunication channel 120 has a greater cost associated with it fortransmitting and/or receiving data than on the low cost communicationchannel 122. For example, a wireless communication channel of the typeused on pagers and wireless computers is an example of a high costcommunication channel because the per transmission unit price is high.Additionally, the cost can take into account factors such as batteryusage, power consumption, bandwidth limits, usage limits, and/or othercost factors. The low cost communication channel 122 might include asynchronization channel, a serial channel, a network channel, aninfrared channel, a HotSync™ channel, and/or some other type ofcommunication channel. Whereas the high cost communication channel 120is expensive, the low cost communication channel 122 is cheap in termsof price, bandwidth, battery consumption, etc.

The unifier 112 and the unifier 114 can be standalone softwareapplications, mail agent plug-ins, mail rules, procmail routines, mailhandlers, part of the mail agent, and/or some other type of program. Theunifier 112 and 114 are able to access messages either directly from themail server serving their respective mailbox or once the mail has beentransferred by the mail agent to the respective client.

A unifier (e.g. the unifier 112 and the unifier 114) can assign eachmessage a distinguishing identifier. This identifier can be incorporatedinto the header of a message, e.g. add a header “X-UNIFY-ID:identifier”. If a message received by the unifier already has anidentifier associated with it, the unifier will not assign a secondidentifier. Again, this can be implemented by examining the messageheaders to ascertain if an X-UNIFY-ID header is present. In someembodiments, an additional Multipurpose Internet Mail Extensions (MIME)section including the identifier is added to message bodies instead ofadding a header.

The identifier itself should be at least unique across the contents ofthe mailboxes being unified. Thus, a simple counter combined with a nameor number associated with the unifier can be used. For example, theunifier 112 could prefix identifiers it creates with“jdoe@wireless.com:” and a number starting from say “0” and incrementingthe counter each time. Similarly, the unifier 114 could prefixidentifiers it creates with “jdoe@corporate.com:” and a number. Othertypes of identifiers could be used such as identifiers dependent on thecontents of one or more message headers and/or the message body.

The unifier (e.g. the unifier 112 and the unifier 114) can send a copyof the message including the identifier to the other mailbox using thecorresponding address. For example, if a message to addressed to“jdoe@corporate.com” from “tbrown@example.com” is received at themailbox 102, then it will be assigned an identifier by the unifier 114.For example, the identifier assigned might be “jdoe@corporate.com:97”. Acopy of the original message—or a portion of the original message—isthen sent to the address 104, “jdoe@wireless.com”. The copy will includethe identifier. In some embodiments, the identifier is included as anadditional header to the message, e.g. “X-UNIFY-ID:jdoe@corporate.com:97”. Similarly, for a message sent to the address104, a copy will be sent to the address 106 with a distinguishingidentifier by the unifier 112. If the copy of the message is excerptedor modified from the original format, this can be so indicated in themessage sent to the other mailboxes.

In some embodiments, the unifier 114 accepts user defined parameters tocontrol which messages and/or which portions of messages are sent to theaddress 104. Because of the high cost of using the high costcommunication channel 120, it may be undesirable to send large messagesand or message attachments to the address 104. In some embodiments, theuser can select whether or not attachments are included when sent to theaddress 104. In some embodiments, the user can select a predeterminedamount of a message to be sent to the address 104, e.g. first 250 words,etc. In some embodiments, the user can request that the unifier 114summarize messages longer than a predetermined amount and send thesummary to the address 104 along with the identifier. Also, the user mayrequest that attachments be translated into a format usable by thehandheld client 108.

The unifier (e.g. the unifier 112 and the unifier 114) can send messageswhen actions occur. The messages can be sent periodically from theunifier 114 to the address 104. The message content for an action wouldtypically be a single line comprising two parts: the identifier and theaction description. For example, if Jane reads the message from“tbrown@example.com” on her handheld client 108, an action message suchas “jdoe@corporate.com:97 read” will be generated. Or, if Jane files themessage the following action can be sent: “jdoe@corporate.com:97 filedbusiness”, etc.

In some embodiments, information about multiple actions are combinedinto a single message. For example, the unifier 114 might send messagesto the address 104 every twenty minutes and at that point all unsentactions are sent. Each action can appear on a separate line of themessage, e.g.:

-   -   jdoe@corporate.com:97 deleted    -   jdoe@wireless.com:32 read    -   jdoe@corporate.com:98 filed business    -   jdoe@corporate.com:90 replied    -   jdoe@wireless.com:30 forwarded        These actions can all be encapsulated inside a MIME section of        an appropriate type to signal to the other unifier (e.g. the        unifier 112) that the message requires processing.        Alternatively, a mail header could indicate that the message        requires processing.

Assuming the above five actions were sent in a message from the unifier114 to the unifier 112, then when the message is received by the unifier112, it will perform the listed actions on the messages on the handheldclient 108. Thus, after receiving the actions and processing them, themessages on the handheld client 108 will look the same as the messageson the client 110. Further, all actions taken on the client 110 will bereflected on the handheld client 108.

The financial costs of the high cost communication channel 120 can beconsidered by examining one wireless plan offered by Palm.Net™ thatcould be accessible to the handheld client 108 for use as the high costcommunication channel 120. The plan allows for 150 Kilobytes (KB) oftransmission each month and charges $0.30 for each additional KB. Forany significant volume of mail, relying on the high cost communicationchannel 120 for unification could quickly become prohibitivelyexpensive. The based monthly amount of 150 KB would cover about 250short messages—including the copies of messages sent by the unifier 114,the copies of mess ages sent by the unifier 112, and/or messagesconveying actions from the unifier 112 and the unifier 114. Further, thebattery consumption and other factors need to be considered in the cost.

Thus, the low cost communication channel 122 can reduce the overall costof the unification process. When the handheld client 108 establishes thelow cost communication channel 122, then the unifier 114 can unify themail across the low cost communication channel 122 and remove anymessages not yet received by the handheld client 108 from the mailbox100 using the communication channel 118. Similarly, any pending messagesthat the unifier 112 has not yet transmitted over the high costcommunication channel 120 can be sent to the unifier 114 via the lowcost communication channel 122.

In this example, the five actions listed above sent in the message bythe unifier 114 to the mailbox 100 have not yet been transferred to thehandheld client 108. When the handheld client 108 connects to the client110 over the low cost communication channel 122, the five actions areperformed on the handheld client 108 and the message with the fiveactions is removed from the mailbox 100. This saves costs because thehandheld client 108 will not retrieve messages it has already seen fromthe mailbox 100 when the high cost communication channel 120 is usednext.

C. Process Flow

FIGS. 2-5 are process flow diagrams describing the unification processaccording to various embodiments of the invention. These could be usedby the unifiers (e.g. the unifier 112 and the unifier 114) to unify theview of multiple mailboxes on multiple mail agents.

FIG. 2 is a process flow diagram for receiving a message without anidentifier according to some embodiments of the invention. At step 200,the message is received by the mail agent from a first mailbox (e.g. themailbox 102). Messages with known identifiers do not have an additionalidentifier generated. For example, if the unifier 114 is set to workonly with the mailbox 102 and the mailbox 100, if a message is receivedwith an identifier such as “someuser@foo.com:1005”, then a newidentifier can be generated. In some embodiments, the user of the client110 is prompted as to whether this is identifier indicates a new mailboxwhich the unifier 114 should unify.

Next, at step 202, a distinguishing identifier is generated for themessage by the unifier on that client (e.g. the unifier 114). Thedistinguishing identifier should be unique across the unified mailboxes.A combination of the address corresponding to the initial mailbox amessage was received at with an incrementing counter can be used as theidentifier. In other embodiments, headers in the message are used togenerate the identifier.

At step 204, a copy, or a portion, of the message is sent to the secondmailbox (e.g. the mailbox 100) with the identifier. In some embodiments,the identifier is included in a message header. In other embodiments,the identifier is included in a MIME section with a copy of the originalmessage in another MIME section.

User defined criteria and system defined limits can control the messagecontents. For example, attachments might be removed and/or translatedinto alternate formats before sending the message to the second mailbox.Messages longer than a certain length can be reduced to a predeterminedsize and/or summarized automatically. Additionally, mail filters can beused such as only unifying messages with a certain priority and/or thatmeet a certain criteria. For example, only messages whose priority isset to urgent could be unified. Another example might be to only unifymessages from senders in a list of important clients. In otherembodiments, these filters might be used to control which messages aresent for delivery over the high cost communication channel 120. In thisembodiment, when the low cost communication channel 122 is employed, theremaining messages can be unified.

The unifier (e.g. the unifier 114) can keep a record of identifiers formessages it sent over the communication channel 118 for delivery to thehandheld client 108. In some embodiments, the unifier can periodicallypoll the mailbox 100 to determine which messages have been delivered totrim the record so it contains only those messages not yet delivered tothe handheld client 108.

Similarly, the unifier 112 on the handheld computer can hold messagesuntil either the high cost communication channel 120 or the low costcommunication channel 122 can be used. In some embodiments, the unifier112 can be set to always wait for access to the low cost communicationchannel 122 to send its messages—including messages with actions. Thisreduces use of the high cost communication channel 120. This may beacceptable because typically a user of the handheld client 108 will beable to use the low cost communication channel 122 when they are nextaccessing their mailbox 102 using the client 110. Therefore in thisembodiment, a user might synchronize their handheld client 108 withtheir client 110 before proceeding to use the mail agent on the client110.

FIG. 3 is a process flow diagram for reflecting actions performed onmessages to the other mailboxes. First at step 300, an action isperformed on a message on a client (e.g. the client 110).

Next, at step 302, a new message is created by the unifier (e.g. theunifier 114) with the identifier of the message on which the action wasperformed and a description of the action. In some embodiments, multipleactions are combined into one message as described above. On thehandheld client 108, step 304 can be skipped because either the messageswill be available on the handheld client 108 when the low costcommunication channel 122 is used next, or they will have already beensent over the high cost communication channel 120 and received by theclient 110. If the high cost communication channel 120 is not being usedby the handheld client 108 for some or all messages, then for thosemessages step 302 can be skipped and step 304 will be performed afterstep 300.

Lastly, at step 304, the identifier and action are stored on the clientin a record of actions. The contents of the mailbox 100 can be polledperiodically by the unifier 114 in some embodiments of the invention todetermined what actions have already been received by the handheldclient 108 and to trim the record of actions.

FIG. 4 is a process flow diagram for unifying the mailboxes over thehigh cost communication channel 120. First, a step 400, the handheldclient 108 connects to its mailbox (e.g. the mailbox 100) over the highcost communication channel 120. The mailbox 100 will contain appropriatemessages from the unifier 114 reflecting messages sent to the mailbox102 as well as actions performed on messages on the client 110.

At step 402, the messages from the mailbox 100 are used to unify theview of the messages in the handheld client 108. If a message in themailbox 100 has no identifier, then the process of FIG. 2 is applied. Ifthe message has an identifier, then it is added to the view. If themessage includes identifiers and actions, the appropriate actions areperformed on messages with the respective identifier.

For example, a new message sent directly to “jdoe@wireless.com” willundergo the process of FIG. 2. A copy of a message sent originally to“jdoe@corporate.com” together with an identifier, e.g.“jdoe@corporate.com:94”, will be added to the unified view. A messagewith identifiers and actions, e.g. the action “jdoe@corporate.com:94read” will be acted upon. Thus, upon receiving the third message withthe action, the message on the handheld client 108 with that identifierwill have its status set to read. The result is that the handheld client108 has a unified view of the mailboxes 100 and 102.

Next, at step 404, the handheld client 108 sends messages it hasreceived but not already sent to the mailbox 102 over the high costcommunication channel 404. This could include the copies of messagesgenerated at step 204 and the messages with actions generated at step302. In some embodiments, step 404 is skipped to reduce the usage of thehigh cost communication channel 120. In other embodiments, messagesmatching certain criteria are sent over the high cost communicationchannel 120, while others are held to be sent over the low costcommunication channel 122.

FIG. 5 is a process flow diagram for unifying the mailboxes over the lowcost communication channel 122. First at step 500, the handheld client108 connects to the client 110 over the low cost communication channel122.

Next, at step 502, the two views are unified. Messages, both the copiesof messages with identifiers and messages with actions, sent by theclient 110 to the mailbox 100 but not yet received by the handheldclient 108 are sent over the low cost communication channel 122 to unifythe message view on the handheld client 108. Similarly, messages on thehandheld client 108 not yet sent to the client 110 are sent over the lowcost communication channel 122 to unify the message view on the client110.

Finally, at step 504, the unifier on the client 110 signals to themailbox 100 to remove messages. This ensures that the next time thehandheld client 108 retrieves messages over the high cost communicationchannel 120, unnecessary messages are not retrieved. This could take theform of a mail message from the unifier 114 indicating which messagesare to be deleted or a proprietary signal between the unifier 114 andthe mail server handling the mailbox 100. For example, a special port onthe mail server might be designated to receive encrypted communicationsfrom the client 108 specifying the messages to be deleted. In otherembodiments, the communication might simply indicate that the views areunified and to remove any messages from the mailbox 100 that originatedfrom the unifier 114.

D. Alternative Embodiments

In some embodiments, the unifier 112 and the unifier 114 are implementedas one or more computer programs. The computer programs can be includedin one or more computer usable media such as CD-ROMs, floppy disks, orother media.

Some embodiments of the invention are included in an electromagneticwave form. The electromagnetic wave form comprises information such asthe unifier 112 and the unifier 114. For example, the electromagneticwave form could include signals sent over a network from a servercomputer to a client computer with the unifier 112 and/or the unifier114.

E. CONCLUSION

The foregoing description of various embodiments of the invention hasbeen presented for purposes of illustration and description. It is notintended to limit the invention to the precise forms disclosed. Manymodifications and equivalent arrangements will be apparent.

1. A method comprising performing a machine-executed operation involvinginstructions for presenting a unified view of a first message sent to afirst mailbox on a second client using a low cost communication channeland a high cost communication channel, a first client having a secondcommunication channel with a second mailbox and a low cost communicationchannel with the second client, the second client capable of beingcoupled in communication with the second mailbox using the high costcommunication channel, wherein the machine-executed operation is atleast one of: A) sending said instructions over transmission media; B)receiving said instructions over transmission media; C) storing saidinstructions onto a machine-readable storage medium; and D) executingthe instructions; wherein said instructions are instructions which, whenexecuted by one or more processors, cause the one or more processors toperform the steps of: receiving the first message at the first client;generating a distinguishing identifier for the first message; sending atleast a portion of the first message and the distinguishing identifierto the second mailbox using the second communication channel; responsiveto an action on the first message on the first client, creating a secondmessage including the distinguishing identifier and a description of theaction; sending the second message to the second mailbox using thesecond communication channel; and selectably causing updating theunified view of the first message on the second client using either thehigh cost communication channel or the low cost communication channel.2. The method of claim 1, wherein the selectably updating the unifiedview further comprises: using the low cost communication channel whenthe second client is coupled in communication with the first client;updating the unified view of the first message on the second clientusing the at least a portion of the first message and the action;removing the at least a portion of the first message and the secondmessage from the second mailbox after updating the unified view.
 3. Themethod of claim 1, wherein the selectably updating the unified viewfurther comprises: using the high cost communication channel when thesecond client is coupled in communication with the second mailbox;receiving the at least a portion of the first message on the secondclient from the second mailbox; receiving the second message on thesecond client using the second message; and updating the unified view ofthe first message on the second client using the second message.
 4. Themethod of claim 1, wherein the high cost communication channel comprisesa wireless communication channel.
 5. The method of claim 1, wherein thelow cost communication channel comprises a synchronization communicationchannel.
 6. The method of claim 1, wherein the action comprises at leastone of reading the first message, replying to the first message,forwarding the first message, classifying the first message, anddeleting the first message.
 7. The method of claim 1, wherein the firstmessage includes an attachment, and wherein the at least a portion ofthe first message comprises a predetermined amount of the first messagewithout the attachment.
 8. A method comprising performing amachine-executed operation involving instructions for presenting aunified view of messages in a first mailbox and a second mailbox,wherein the first mailbox is hosted by a first host and the secondmailbox is hosted by a second host, wherein the machine-executedoperation is at least one of: A) sending said instructions overtransmission media; B) receiving said instructions over transmissionmedia; C) storing said instructions onto a machine-readable storagemedium; and D) executing the instructions; wherein said instructions areinstructions which, when executed by one or more processors, cause theone or more processors to perform the steps of: a first client of thefirst mailbox receiving a first message addressed to the first mailbox;determining whether the first message has been assigned an identifier;if the first message has not been assigned an identifier, then:generating a first identifier that is unique relative to otheridentifiers assigned to the messages by the first client of the firstmailbox and a second client of the second mailbox, and sending at leasta portion of the first message to the second mailbox; detecting anaction taken on the first message by the first client; and in responseto detecting the action, transmitting a second message to the secondclient that includes the first identifier and a description of theaction.
 9. The method of claim 8, wherein: a set of channelcommunications between the first client and the second client includes afirst channel of communication and a second channel of communication;the steps further include selecting the first channel of communication;and wherein the step of sending the first message includes sending thefirst message via the first channel.
 10. The method of claim 9, whereinthe first channel of communication does not require participation of thesecond host to transmit the first message.
 11. The method of claim 10,wherein the second channel of communication includes a wireless channelof communication.
 12. The method of claim 9, wherein selecting the firstchannel of communication includes selecting the first channel based onrelative cost between the first channel and the second channel.
 13. Themethod of claim 9, wherein sending the first message is deferred until aconnection is established over the first channel.
 14. The method ofclaim 8, wherein the steps further include, if the first message hasbeen assigned an identifier, foregoing sending at least a portion of thefirst message to the second mailbox.
 15. The method of claim 8, whereinsending the second message causes the action to be repeated on thesecond client.